home
***
CD-ROM
|
disk
|
FTP
|
other
***
search
/
Tech Arsenal 1
/
Tech Arsenal (Arsenal Computer).ISO
/
tek-11
/
fprotems.zip
/
PROPOPS.DOC
< prev
next >
Wrap
Text File
|
1993-01-04
|
4KB
|
73 lines
PROPOPS.DOC
PROPOPS Template documentation.
A UI2 Template c. Ellen J. Sander, 1989
Generates: Code for FoxPro user-defined popup menus.
Requires: Named box(es) on the screen at generation time,
with one or more options in it/them.
Function library used: Propops.TLB
Propops.TEM generates popup menus using the new DEFINE MENU...DEFINE BAR
syntax, from boxes with menu options designed in the UI2 editor.
ProPops.TEM requests a FoxPro COLOR SCHEME from the developer at generation
time and uses this color scheme for all menus in the set. A set of popup
menus in a specific color scheme may then be developed a screenful at a
time.
To define a FoxPro menu in the UI2 editor, create a box and enter a name
for it in the Name slot of the box definition menu. Slot 1 in the menu
box's definition menu is available for MESSAGE code. (aside: Is there a
beter name to call that object?) Type the keyword MESSAGE and a quote-
delimited "message string." If the expression gets long, (up to 79
characters are legal in FoxPro) the template will split the line in the
generated code wherever you type a semi-colon in the slot.
PROPOPS.TEM supports two types of FoxPro popup menu objects:
1.FIXED SIZE, MULTI-PROMPT POPUPS w/hard coded prompts
PROMPT, MESSAGE and SKIP code is generated when you create and
attribute the menu as follows:
Create and size the menu box at the screen location where you want the
menu to appear in your application. Create prompts as options for the
menu. Type the prompt directly into the menu option on the design screen.
In the menu option definition window, you may specify a message string for
the prompt (messages are allowed for options as well as menus) in the
dedicated Message String slot. You may also (or alternately) enter any
SKIP/SKIP FOR <logical condition> in the message slot in addition to any
message text entered. Do not enter a trigger character. The trigger will
automatically be the first character of the Prompt.
2. VARIABLE SIZED POPUPS using fields or files as prompts
Popup menus using PROMPT FIELD, FILES/FILES LIKE... STRUCTURE will be
generated if you design the popup as follows:
Draw the box on the screen with the upper left corner positioned where you
want the popup menu to start. The size and shape of the box on screen are
insignificant; at run-time the menu will size itself, and the prompts will
scroll if there are more of them than will fit from the top of the popup
to the bottom of the FoxPro screen. Place one and *only one* option in the
menu (it can be any height). You needn't type any text into that option,
it is simply a marker for the template. On the other hand, you can type
anything you like in there: the template will ignore it.
Open the option definition window from the UI2 Menus menu and enter PROMPT
FIELD <fieldname>, PROMPT FILES/FILES LIKE <skeleton>, PROMPT STRUCTURE
code into line 1 of the Option Action Code box. Type a MESSAGE clause, if
any, into the dedicated message slot. (The SKIP clause is inapplicable
with variable sized popups using fields or files as prompts).
All functions except digest_text(), from the WallSoft-supplied template
libraries, are specifically written for this template.
More complete instructions for using this template are in January, 1990
issue of DBMS magazine. However, the code printed in that issue has
errors which were editorially produced, and the listings on their BBS, at
the time of this writing also had the errors.